Personal Network Access Control System and Method

ABSTRACT

A server is provided that includes a processor such that for a Session Initiation Protocol (SIP) request containing a Uniform Resource Identifier (URI) identifying the first device, the processor is programmed to promote adding a URI and redirecting the SIP request to a second device. The added URI used by the second device to invoke a Personal Network Management (PNM) Controller function.

BACKGROUND

Traditionally, a single integrated device with integrated radio accessmeans formed the user equipment (UE) and was used for access to mobilecommunication services. However, many users now possess more than onedevice for mobile communication services. Such devices may be connectedto form a personal network (PN). The devices differ in theircapabilities, and these capabilities qualify the devices more or lessfor specific end-to-end applications or media, such as audio, video, orpictures.

Personal network management (PNM) allows users to manage their devicesand PNs. The considered management functions of PNM include the setupand configuration of PNs, the personalization for the termination ofservices within a PN, and the enablement of secure connections betweenthe devices or personal network elements (PNEs).

PNM addresses the management of multiple devices or UEs belonging to asingle user or subscriber. Personal UE network features enable themanagement of multiple UEs belonging to a single PN user. In particular,the needs of users with more than one terminal and subscription areaddressed, e.g. ordinary handset for telephony, car phone, PDA foremails when the user is on the move, and a data card with laptop whenthe user is in a semi-stationary mode. Although such devices are mainlyheld for a particular usage, many are able to support more than one sortof service, e.g. telephony may be supported by several of the previouslymentioned devices. However, PNEs are not aware of the presence of otherPNEs belonging to a user.

PNM can apply to any calls or sessions or messages (including but notlimited to telephony calls, Push to Talk Sessions, Messaging Sessions)as well as individual messages such as Instant Messages or ShortMessages (SMS).

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of this disclosure, reference is nowmade to the following brief description, taken in connection with theaccompanying drawings and detailed description, wherein like referencenumerals represent like parts.

FIG. 1 illustrates a personal network with a PNM Controller UE and a PNMControllee UE according to an embodiment of the disclosure.

FIG. 2 illustrates a high level sequence of personal network accesscontrol according to an embodiment of the disclosure.

FIG. 3 illustrates another high level sequence of personal networkaccess control according to an embodiment of the disclosure.

FIG. 4 illustrates a PNM Controller UE determining that a SIP INVITE hasbeen redirected by the PNM AS according to an embodiment of thedisclosure.

FIG. 5 illustrates signaling flows for PN access control according to anembodiment of the disclosure.

FIG. 6 is a diagram of a wireless communications system including userequipment operable for some of the various embodiments of thedisclosure.

FIG. 7 is a block diagram of user equipment operable for some of thevarious embodiments of the disclosure.

FIG. 8 is a diagram of a software environment that may be implemented onuser equipment operable for some of the various embodiments of thedisclosure.

FIG. 9 is an illustrative general purpose computer system suitable forsome of the various embodiments of the disclosure.

FIG. 10 illustrates an exemplary cellular network according to anembodiment of the disclosure.

FIG. 11 depicts a detailed view of a cell within the exemplary cellularnetwork.

DETAILED DESCRIPTION

It should be understood at the outset that although illustrativeimplementations of one or more embodiments of the present disclosure areprovided below, the disclosed systems and/or methods may be implementedusing any number of techniques, whether currently known or in existence.The disclosure should in no way be limited to the illustrativeimplementations, drawings, and techniques illustrated below, includingthe exemplary designs and implementations illustrated and describedherein, but may be modified within the scope of the appended claimsalong with their full scope of equivalents.

According to one embodiment, a server is provided that includes aprocessor such that for a Session Initiation Protocol (SIP) requestcontaining a Uniform Resource Identifier (URI) identifying the firstdevice, the processor is programmed to promote adding a URI andredirecting the SIP request to a second device. The added URI used bythe second device to invoke a Personal Network Management (PNM)Controller function.

According to another embodiment, a method is provided of redirecting aSession Initiation Protocol (SIP) request. The method includes receivinga SIP request addressed to a first device, the SIP request containing aUniform Resource Identifier (URI) identifying the first device. Themethod includes adding a URI to the SIP request, and redirecting the SIPrequest to a second device. The presence of the added URI invokes acontroller function that allows the second device to identify the SIPrequest as a redirected SIP request for the first device.

According to other embodiments, a server is provided that includes aprocessor programmed to promote including in a request an identifieridentifying a Personal Network Management (PNM) Controller function.

According to one embodiment, a user equipment (UE) is provided thatincludes a processor such that responsive to receiving a SessionInitiation Protocol (SIP) request including a Uniform ResourceIdentifier (URI) identifying a Personal Network Management (PNM)Controller function, the processor is programmed to promote performingthe PNM Controller function.

In another embodiment, a user equipment (UE) is provided that includes aprocessor such that responsive to receiving a Session InitiationProtocol (SIP) request including an identifier identifying a PersonalNetwork Management (PNM) Controller function, the processor programmedto promote providing PNM Controller function.

The functionality enabled by PNs comprises PN UE redirection and PNaccess control. Registration, configuration, and interrogationprocedures for PNM are supported via IMS capable personal network UEsvia a web client or by administrative procedures.

With regard to PN UE redirection, users may not always carry all oftheir devices with them but still want to be reachable. Currently,management of all of the devices for the PN user includes settingforwarding options, switching on and off the devices, and providingothers with multiple addresses.

With regard to PN access control, FIG. 1 illustrates a personal network(PN) 100 with a PNM Controller UE 102 and a PNM Controllee UE 104according to an embodiment of the disclosure. For example, a family witha young child may establish the PN 100 for the family with the parent UEbeing the PNM Controller UE 102 and the child UE being the PNMControllee UE 104. The PN user may additionally modify the access levelsof each UE of the PN 100 to be public or private. For example, theparent or PNM Controller UE 102 is public and can receive calls (orsessions) from outside the PN 100 while the child or PNM Controllee UE104 is private and can only receive calls (or sessions) from within thefamily PN 100.

A personal network management application server (PNM AS) 106 providesaccess control that allows the PNM Controller UE 102 to determine whichUEs external to the PN 100 are allowed to become guest UEs that cancontact the PNM Controllee UE 104. Thus, a parent can determine who cancontact their child. The identities of external UEs that can contact thePNM Controllee UE 104 can be pre-defined by the PNM Controller UE 102 inan access control list 108 on PNM AS 106. Therefore, when the PNMControllee UE 104 receives a call (or session) from an external UE 110that is on the access control list 108, the PNM AS 106 passes the call(or session) on to the PNM Controllee UE 104. If the external UE 110 wasnot on the access control list 108, the PNM Controller UE 102 can beinformed that the external UE 110 is attempting to place a call (orsession) to the PNM Controllee UE 104. One way this can be accomplishedis by having the PNM AS 106 redirect the incoming call (or session) forthe PNM Controllee UE 104 to the PNM Controller UE 102. The PNMController UE 102 can then decide, such as manually by the user on acall-by-call basis, to have the PNM AS 106 redirect the call (or sessionor message) to the PNM Controllee UE 104 or reject the call (or sessionor message). The PNM Controller UE 102 can even accept the call (orsession or message) and then after communicating with the caller decidewhether to transfer the call (or session or message) to the PNMControllee UE 104 or end the call (or session or message).

FIG. 2 illustrates a high level sequence 200 of personal network accesscontrol according to an embodiment of the disclosure. In FIG. 2, it isassumed that the originating UE (i.e., external UE 110) is a guest UEand is configured in the access control list 108 of the PNM ControlleeUE 104. When the PNM AS 106 receives an initial request message from aCall Session Control Function (S-CSCF#1), the PNM AS 106 verifies thatthe external UE 110 matches an entry in the access control list 108 ofthe PNM Controllee UE 104 and sends the initial request message to thePNM Controllee UE 104.

At flow 201, the S-CSCF#1 receives an initial request message from theexternal UE 110 to the PNM Controllee UE 104. The S-CSCF#1 invokes thetermination service control logic required for the PNM Controllee UE 104and evaluates the initial filter criteria at flow 202. The S-CSCF#1 thenforwards the initial request message to the PNM AS 106 at flow 203 as aresult of executing the initial filter criteria. In the privacy modeprocessing at flow 204, the PNM AS 106 extracts the source anddestination addresses from the initial request message. The PNM AS 106confirms that the PNM Controllee UE 104 is a controllee UE. Using thisas a key, PNM AS 106 then searches its database for the PN 100 of thePNM Controllee UE 104 to find if the external UE 110 is configured inthe access control list 108 for the PNM Controllee UE 104. In this case,it is assumed that the external UE 110 is in the access control list 108and is allowed to initiate sessions with or send messages to the PNMControllee UE 104. At flow 205, the PNM AS 106 sends the initial requestmessage to the S-CSCF#1. The S-CSCF#1 then routes the initial requestmessage to the PNM Controllee UE 104 at flow 206.

FIG. 3 illustrates another high level sequence 300 of personal networkaccess control according to an embodiment of the disclosure. At flow301, external UE 110 sends an initial request message to the PNMControllee UE 104. The initial request message is received by the PNM AS106, and the privacy mode processing is executed at flow 302. In thisembodiment, it is assumed that the external UE 110 is not on the accesscontrol list 108. At flow 303, the PNM AS 106 queries the PNM ControllerUE 102 on how to proceed with the initial request message. In theprivacy decision processing flow 304, the query info is shown to the PNuser of the PNM Controller UE 102. For example, the external UE 110calling the PNM Controllee UE 104, with options for the controlling userto select: 1: Allow Controllee, 2: Deny Controllee, 3: Allow Controlleeand save policy, 4: Deny Controllee and save policy, 5: Accept atController. The PN user of the PNM Controller UE 102 may thenallow/disallow and possibly save this option for future calls. Thedecision whether to Allow, Deny, or Accept is sent in the response tothe query. The response message is sent to the PNM AS 106 in flow 305.In the privacy response processing flow 306, the PNM AS 106 determinesthe action directed by the PN user of the PNM Controller UE 102. At flow307, it is assumed that the PN user of the PNM Controller UE 102 hasallowed the call to go through to the PNM Controllee UE 104, and the PNMAS 106 sends the initial request message to the PNM Controllee UE 104.

Since there exists the possibility for the PNM Controller UE 102 toaccept the call (or session or message), flow 203 may be implementedusing a SIP INVITE or other SIP Request such as a SIP MESSAGE and sothis is maybe similar to call forwarding or Message forwarding.Therefore, there may need to be a way for the PNM Controller UE 102 toidentify that this request is a PNM access control request intended forthe PNM Controller application as opposed to an ordinary call or messagereceived by the PNM Controller UE 102 or call/Message forwarding.

Accordingly, the disclosure provides a system and method by which thePNM Controller UE 102 can determine that the incoming SIP INVITE or SIPMESSAGE or other SIP Request is a redirection as a result of the PNM AS106 redirecting a call, session, or Message for the PNM Controllee UE104 to the PNM Controller UE 102 so that the PNM Controller UE 102 canhandle the SIP INVITE or SIP MESSAGE or other SIP Request correctly.

It may be useful if the SIP INVITE or SIP MESSAGE or other SIP requestconveys the following information to the PNM Controller UE 102:

1: That this request is a PNM access control request intended for thePNM Controller application;

2: The identity of the originator of the request; and

3: The identity of the PNM Controllee UE 104 to whom the request wasoriginally addressed.

The present disclosure proposes, according to one embodiment, severaltechniques for these purposes such as:

1: defining a new feature tag for the PNM Controller application andinclude this feature tag in an Accept-Contact header in order toidentify that this request is a PNM access control request intended forthe PNM Controller application;

2. defining an IMS Application Reference Identifier (IARI) value for thePNM Controller application and include this in the g.3gpp.app_reffeature tag in an Accept-Contact header in order to identify that thisrequest is a PNM access control request intended for the PNM Controllerapplication;

3: including the P-Asserted-Identity header from the original request inorder to identity of the originator of the request; and/or

4: including in the Request URI the target URI-parameter (as defined inRFC 4458) the URI of the PNM Controllee UE 104 to whom the request wasoriginally addressed.

Other alternatives provided according to various embodiments of thepresent disclosure are as follows:

This identifier could be: 1) A URI that identifies the PNM Controller,2) A New SIP URI parameter in the URI, 3) Including in the URI a TargetURI parameter (defined in RFC 4458) and setting the Target parameter tohave a unique URI that indicates that the PNM Controller applicationshould be invoked. E.g.

INVITE sip:PN_UE1a@home1.net;target=PNM- Controller.UE-1a@home1.net

Including in the URI a Target URI parameter (defined in RFC 4458) andsetting the Target parameter to the URI of the PNM Controllee UE thatthe session was originally addressed to in order to cause the PNMController application should be invoked. E.g.

INVITE sip:PN_UE1a@home1.net;target=PN_UE-1b@home1.net

-   -   Including in an Accept-Contact header (as per RFC 3841) a Media        Feature tag that indicates PNM Controller.    -   Including in an Accept-Contact header a g.3gpp.app_ref feature        tag containing an IMS Communication Service Identifier (ICSI)        value or IMS Application Reference Identifier (IARI) value that        identifies the PNM Controller should be invoked. NOTE that the        PNM Controller UE will previously at registration have        registered the Media Feature tag in the Contact header of the        SIP REGISTER request as per RFC 3840.    -   A new SIP (e.g. a P-Header)    -   In order to enable the PNM Controller (UE-1 a) to identify this        as a PNM Controller related request as opposed to an ordinary        call forwarding the PNM AS adds to the SIP INVITE request (in        Step 14) the following identifiers: 1) A PNM Specific        URI-Parameter (3GPP-pnm-cntrlr) is added to the URI of UE-1a in        the Request URI and/or the URI in the To header, 2) A        History-Info header is included containing a Reason header        indicating this is a PNM Controller related forwarding        (Reason=3GPP-PNM;cause=1, where 1 indicates PNM Controller        related forwarding). The UE-1 a URI in the History-Info header        also may contain the PNM Specific URI-Parameter        (3GPP-pnm-cntrlr), 3) An Accept-Contact header containing a        feature tag that identifies the PNM Controller When PNM        Controller UE-1 a receives the SIP INVITE it can use the        following aspects to determine that this is a PNM Controller        related request as opposed to ordinary call forwarding; 1)        Presence of the PNM Specific URI-Parameter (3GPP-pnm-cntrlr) is        in the P-Called-Party-ID header and/or the URI in the To        header, 2) Presence of a Reason header indicating this a PNM        Controller related forwarding (Reason=3GPP-PNM;cause=1, where 1        indicates PNM Controller related forwarding) in the History-Info        header. 3) Presence of UE-1 a the PNM Specific URI-Parameter        (3GPP-pnm-cntrlr) in the URI in the History-Info header. 4)        Presence of an media feature tag (or parameter value of the        media feature tag) in an Accept-Contact header that identifies        the PNM Controller.

When PNM Controller UE-1a receives the SIP INVITE it can use thefollowing aspects to determine that this is a PNM Controller relatedrequest as opposed to ordinary call forwarding: 1) Presence of thetarget URI—in the P-Called-Party-ID header containing either a URI thatidentifies the PNM Controller or the URI of the Controllee UE, 2)Presence of an media feature tag (or parameter value of the mediafeature tag) in an Accept-Contact header that identifies the PNMController, 3) The presence of a PNM specific URI-parameter(3GPP-pnm-cntrlr) in the Contact header that was inserted by the PNMApplication Server.

While the target URI-parameter as defined in RFC 4458 was originallydefined with services like voicemail and interactive voice response(IVRs), its usage is not restricted to these applications and can beused by any application that needs to know the original target.

The PNM Controller application is an application in the PNM ControllerUE 102 that needs to determine the URI that the request was addressed towhen it was processed by the PNM AS 106.

Another reason to use the Accept-Contact header and define an IARI valueto indicate the PNM Controller application is that it is possible thatthe user of the PNM Controller UE 102 may have multiple UEs registeredwith the same public user identity and only one of them is PNMController capable (or PNM Controller enabled). In this situation, therequest needs to be prioritized to be routed to the UE that performs thePNM Controller function. Use of the Accept-Contact header and an IARIvalue or some other feature tag to indicate the PNM Controller satisfiesthis requirement.

In one embodiment, the disclosure relates to using the following SIPresponses:

1: a 302 (Moved Temporarily) response or some other 3XX response or 4xxresponse to allow the request to be forwarded to the PNM Controllee UE104;

2: a 480 (Temporarily Unavailable) response or some other 4XX responseto deny the request; and

3: a 200 (OK) response or some other 2xx response (such as a 202Accepted) response) to accept the call.

If the user decides to save the policy, a PN Configuration mechanism(using XCAP) may be used to add the policy to the access control list108.

The History-Info header is also included (as per normal call forwarding)and contains the URI that the request was addressed to when it isprocessed by the PNM AS 106 along with the contents of the Request-URIof the forwarded request (including the target URI-parameter).

History-Info: <sip:PN_UE2b@home2.net>;index=1,  <sip:PN_UE2a@home2.net;target=PN_UE-   2b@home2.net>;index=1.1,

The History-Info header from the initial request is included in the 302(Moved Temporarily) response, and the PNM AS 106 then includes theHistory-Info header in the redirected request to the PNM Controllee UE104. This provides information to the PNM Controllee UE 104 that therequest was first directed to the PNM Controller application. Thefollowing example shows the information the PNM Controllee UE 104receives in the History-Info header after the PNM Controller UE 102 hasallowed the PNM Controllee UE 104 to receive the request.

History-Info: <sip:PN_UE2b@home2.net>;index=1,<sip:PN_UE2a@home2.net;target=PN_UE- 2b@home2.net>;index=1.1,<sip:PN_UE2b@home2.net?Reason=SIP;cause=302>;index=1.2

From this information, the PNM Controllee UE 104 can tell that therequest was originally addressed to it (PN_UE2b@home2.net) and wasforwarded to the PNM Controller UE 102 (PN_UE2a@home2.net) with the PNMControllee UE 104 as the target. The request was then redirected to thePNM Controllee UE 104 by the PNM Controller UE 102.

Accordingly, when the PNM AS 106 redirects the call (or session) to thePNM Controller UE 102, the PNM Controller UE 102 needs to be able toidentify the call (or session or message) as a redirected call (orsession or message) due to the PNM AS 106 redirecting a call (or sessionor message) for the PNM Controllee UE 104 to the PNM Controller UE 102.Specifically, when a SIP INVITE or other SIP Request is redirected tothe PNM Controller UE 102 by the PNM AS 106, the PNM Controller UE 102needs to be able to identify the SIP INVITE or SIP Request as aredirection due to the PNM AS 106 redirecting a call (or session ormessage) for the PNM Controllee UE 104 to the PNM Controller UE 102, asopposed to an ordinary call (or session or message) received by the PNMController 102 or call/message forwarding.

According to an embodiment of the disclosure as illustrated in FIG. 4,in order for the PNM Controller UE 102 to determine that a SIP INVITE402 has been redirected by the PNM AS 106, the outgoing SIP INVITE 402may include an identifier 404 in the SIP message that identifies thatthe SIP message has be redirected due to the PNM AS 106. The identifier404 could be:

1: a URI that identifies a PNM Controller application 406;

2: a new SIP URI parameter in the URI;

3: a target URI parameter (as defined in RFC 4458) included in the URIsetting, the target parameter set to a unique URI that indicates thatthe PNM Controller application 406 should be invoked;

a target URI parameter (as defined in RFC 4458) included in the URIsetting, the Target parameter set to the URI of the PNM Controllee UE104 that the session was originally addressed to in order to cause thePNM Controller application 406 to be invoked;

4: a Media Feature tag included in an Accept-Contact header (as per RFC3841), the Media Feature tag indicates the PNM Controller application406 (The PNM Controller UE 102 will have previously registered the MediaFeature tag in the Contact header of the SIP REGISTER request as per RFC3840.);

5: a g.3gpp.app_ref feature tag included in an Accept-Contact header,the g.3gpp.app_ref feature containing an IMS Communication ServiceIdentifier (ICSI) value or an IMS Application Reference Identifier(IARI) value that identifies that the PNM Controller application 406should be invoked; and/or

6: a new SIP header (e.g., a P-Header).

FIG. 5 illustrates signaling flows for PN access control according to anembodiment of the disclosure.

The steps prior to flow 1 are according to the standard proceduresspecified in TS 24.228[10].

FLOW 1. INVITE#1 (I-CSCF#2 to S-CSCF#2)

I-CSCF-2 forwards the INVITE#1 to S-CSCF#2 after invocation of locationQuery. An example of the INVITE#1 may be as follows:

1: SIP INVITE Request (I-CSCF#2 to S-CSCF#2)

INVITE sip:PN_UE2b@home2.net Via:SIP/2.0/UDPicscf2.home2.net;branch=z9hG4bK871y12.1, SIP/2.0/UDPscscf1.home1.net;branch=z9hG4bK332b23.1, SIP/2.0/UDPpcscf1.visited1.net;branch=z9hG4bK240f34.1, SIP/2.0/UDP[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp; branch=z9hG4bKnashds7Max-Forwards: 65 Route: <sip:scscf2.home2.net;lr>Record-Route:<sip:scscf1.home1.net;lr>,<sip:pcscf1.visited.net;lr>P-Asserted-Identity: “John Doe” <sip:UE1@home1.net> Privacy: none From:<sip:UE1@home1.net>;tag=157893 To: <sip:UE2b@home2.net> Cseq: 127 INVITECall-ID:131243vdse Supported: precondition, 100rel,gruu Accept-Contact:*;g.3gpp.app_ref=“urn%3Aurn-xxx%3gpp- service.ims.icsi.mmtel”P-Asserted-Service: urn:urn-xxx:3gpp-service.ims.icsi.mmtel Contact:<sip:PN_UE2b@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0- a765-00a0c91e6bf6> Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE,REFER, MESSAGE Content-Type: application/sdp Content-length: (...) SDPNOT SHOWN

FLOW 2. 100 Trying

S-CSCF#2 responds to the INVITE#1 request with a 100 Trying provisionalresponse. An example of the 100 Trying provisional response may be asfollows:

2: SIP 100 Trying

SIP/2.0 100 Trying Via:SIP/2.0/UDPicscf2.home2.net;branch=z9hG4bK871y12.1, SIP/2.0/UDPscscf1.home1.net;branch=z9hG4bK332b23.1, SIP/2.0/UDPpcscf1.visited1.net;branch=z9hG4bK240f34.1, SIP/2.0/UDP[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp; branch=z9hG4bKnashds7 From:<sip:UE1@home1.net>;tag=157893 To: <sip:UE2b@home2.net> Cseq: 127 INVITECall-ID:131243vdse Content-Length: 0

FLOW 3. Evaluation of Initial Filter Criteria

S-CSCF#2 validates the service profile of this subscriber and evaluatesthe initial filter criteria.

FLOW 4. INVITE#1(S-CSCF#2 to PNM AS)

S-CSCF#2 forwards the INVITE#1 request to PNM AS based upon the initialfilter criteria (IFCs). An example of the resulting INVITE#1 may be asfollows:

4: SIP INVITE request (S-CSCF#1 to PNM AS)

INVITE sip:PN_UE2b@home2.net Via: SIP/2.0/UDPscscf2.home2.net;branch=z9hG4bwt871y12.1, SIP/2.0/UDPicscf2.home2.net;branch=z9hG4bK871y12.1, SIP/2.0/UDPscscf1.home1.net;branch=z9hG4bK332b23.1, SIP/2.0/UDPpcscf1.visited1.net;branch=z9hG4bK240f34.1, SIP/2.0/UDP[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp; branch=z9hG4bKnashds7Max-Forwards: 64 Route: <sip:pnmas.home2.net;lr> Record-Route: <sip:scscf2.home1.net;lr>,<sip:scscf1.home1.net;lr>, <sip:pcscf1.visited.net;lr> P-Asserted-Identity: “John Doe”<sip:UE1@home1.net> Privacy: none From: <sip:UE1@home1.net>;tag=157893To: <sip:UE2b@home2.net> Cseq: 127 INVITE Call-ID:131243vdse Supported:precondition,100rel,gruu Accept-Contact: *;g.3gpp.app_ref=“urn%3Aurn-xxx%3gpp-service.ims.icsi.mmtel” P-Asserted-Service:urn:urn-xxx:3gpp-service.ims.icsi.mmtel Contact:<sip:PN_UE2b@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0- a765-00a0c91e6bf6> Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE,REFER, MESSAGE Content-Type: application/sdp Content-length: (...) SDPNOT SHOWN

FLOW 5. 100 Trying

The PNM AS 106 responds to the INVITE#1 request with a 100 Tryingprovisional response. An example of the resulting 100 Trying provisionalresponse may be as follows:

5: SIP 100 Trying

SIP/2.0 100 Trying Via: SIP/2.0/UDPscscf2.home2.net;branch=z9hG4bwt871y12.1, SIP/2.0/UDPicscf2.home2.net;branch=z9hG4bK871y12.1, SIP/2.0/UDPscscf1.home1.net;branch=z9hG4bK332b23.1, SIP/2.0/UDPpcscf1.visited1.net;branch=z9hG4bK240f34.1, SIP/2.0/UDP[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp; branch=z9hG4bKnashds7 From:<sip:UE1@home1.net>;tag=157893 To: <sip:UE2b@home2.net> Cseq: 127 INVITECall-ID:131243vdse Content-Length: 0

FLOW 6. PNM access control

The PNM AS 106 invokes the Private network service logic. BecauseUE1@home1.net is not on the <PNAccessControlList> of PN_UE-2b@home2.netin this example, the PNM Controller application 406 needs to becontacted.

FLOW 7. INVITE#2 (PNM AS to S-CSCF#2)

The PNM AS 106 generates a new invite message called INVITE#2 and sendsit to S-CSCF#1 in order to interact with the PNM Controller application406. An example of the resulting INVITE#2 may be as follows:

7: SIP INVITE Request (PNM AS to S-CSCF#2)

INVITE sip:PN_UE2a@home2.net;target=PN_UE-2b@home2.net Via: SIP/2.0/UDPpnmas.home2.net;branch=z9hG4bwt871y12.1 Max-Forwards: 70 Route:<sip:scscf2.home2.net;lr> P-Asserted-Identity: “John Doe”<sip:UE1@home1.net> Privacy: none From: <sip:pnmas.home1.net>;tag=r3rw33To: <sip:PN_UE2a@home2.net> Cseq: 127 INVITE Call-ID:131243vdseSupported: precondition, 100rel, histinfo Contact: <sip:pnmas.home2.net>History-Info: <sip:PN_UE2b@home2.net>;index=1, <sip:PN_UE2a@home2.net;target=PN_UE-2b@home2.net>;index=1.1Accept-Contact:*;g.3gpp.app_ref=“urn%3Aurn-xxx%3A3gpp- application.ims.iari.PNM-Controller” P-Asserted-Service:urn:urn-xxx:3gpp-service.ims.icsi.mmtel Allow: INVITE, ACK, CANCEL, BYE,PRACK, UPDATE, REFER, MESSAGE Content-Type: application/sdpContent-length: (...) SDP NOT SHOWN

As illustrated above, the resulting INVITE#2 provides the followinginformation:

Request-URI: contains the URI of the PNM Controller UE(PN_UE2a@home2.net) obtained from the <PNController> element along withthe target URI-parameter which contains the URI from the originalRequest-URI (PN_UE-2b@home2.net).

P-Asserted-Identity: contains the identity of the originator (“JohnDoe”<sip:UE1@home1.net>).

From: contains the SIP URI of the PNM AS 106 (sip:pnmas.home1.net).

To: contains the URI of the PNM Controller UE 102 (UE2a@home2.net).

Supported: contains the following option tags: precondition, 100rel,histinfo.

Contact: contains a SIP URI that contains the IP address or FQDN of thePNM AS 106.

History-info: contains the URIs from the original Request-URI(PN_UE-2b@home2.net) and the URI of the PNM Controller UE 102(PN_UE2a@home2.net) along with the target parameter set to the URI ofthe Controllee (PN_UE-2b@home@2.net). The PNM Controller may look to thecontents of the History-Info header and responsive to finding the targetparameter set to the URI of the Controllee, invoke the PNM Controllerfunction.

Accept-Contact: contains the g.3gpp.app_ref media feature tag with theIARI value “urn %3Aurn-xxx %3A3gpp-application.ims.iari.PNM-Controller”.

FLOW 8. 100 Trying

S-CSCF#2 responds to the INVITE#2 request with a 100 Trying provisionalresponse. An example of the resulting 100 Trying provisional responsemay be as follows:

8: SIP 100 Trying

SIP/2.0 100 Trying Via: SIP/2.0/UDPpnmas.home2.net;branch=v7hG4bwt171y12.1 From:<sip:pnmas.home1.net>;tag=r3rw33 To: <sip:PN_UE2a@home2.net> Cseq: 127INVITE Call-ID:131243vdse : Content-Length: 0

FLOW 9. INVITE#2 (S-CSCF#2 to P-CSCF#2a)

S-CSCF#2 forwards the INVITE#2 request to P_CSCF#2a. An example of theresulting INVITE#2 may be as follows:

9: SIP INVITE request (S-CSCF#2 to P-CSCF#2a)

INVITE sip:[5555::eee:fff:aaa:bbb]:8805;comp=sigcomp SIP/2.0 Via:SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bwt871y12.1, SIP/2.0/UDPpnmas.home2.net;branch=z9hG4bwt871y12.1 Max-Forwards: 69 Route:<sip:pcscf2a.visited2.net;lr> Privacy: none From:<sip:pnmas.home1.net>;tag=r3rw33 To: <sip:PN_UE2a@home2.net> Cseq: 127INVITE Call-ID:131243vdse Supported: precondition, 100rel, histinfoContact: <sip:pnmas.home2.net> History-Info:<sip:PN_UE2b@home2.net>;index=1, <sip:PN_UE2a@home2.net;target=PN_UE-2b@home2.net>;index=1.1Accept-Contact:*;g.3gpp.app_ref=“urn%3Aurn-xxx%3A3gpp- application.ims.iari.PNM-Controller” P-Asserted-Service:urn:urn-xxx:3gpp-service.ims.icsi.mmtel Allow: INVITE, ACK, CANCEL, BYE,PRACK, UPDATE, REFER, MESSAGE P-Called-Party-ID:<sip:PN_UE2a@home2.net;target=PN_UE- 2b@home2.net> Content-Type:application/sdp Content-length: (...) SDP NOT SHOWN

10. 100 Trying

P-CSCF#2a responds to the INVITE#2 request with a 100 Trying provisionalresponse. An example of the resulting 100 Trying provisional responsemay be as follows:

10: SIP 100 Trying

SIP/2.0 100 Trying Via: SIP/2.0/UDPscscf2.home2.net;branch=z9hG4bwt871y12.1, SIP/2.0/UDPpnmas.home2.net;branch=z9hG4bwt871y12.1 From:<sip:pnmas.home1.net>;tag=r3rw33 To: <sip:PN_UE2a@home2.net> Cseq: 127INVITE Content-Length: 0

FLOW 11. INVITE #2 (P-CSCF#2a to UE-2a)

P-CSCF#2a sends the INVITE#2 to UE-2a (PNM Controller UE 102). Anexample of the resulting INVITE#2 may be as follows:

11: SIP INVITE request (P-CSCF#2a to UE-2a)

INVITE sip:[5555::eee:fff:aaa:bbb]:8805;comp=sigcomp SIP/2.0 Via:SIP/2.0/UDP pcscf2a.visited2.net;branch=z9hG4bK240f34.1, SIP/2.0/UDPscscf2.home2.net;branch=z9hG4bwt871y12.1, SIP/2.0/UDPpnmas.home1.net;branch=k9hG4bwt871y12.1 Max-Forwards: 68 Record-Route:<sip:pcscf2a.visited2.net;lr>, <sip:scscf2.home2.net;lr> Privacy: noneFrom: <sip:pnmas.home1.net>;tag=r3rw33 To: <sip:PN_UE2a@home2.net> Cseq:127 INVITE Call-ID:131243vdse Supported: precondition, 100rel, histinfoContact: <sip:pnmas.home2.net> History-Info:<sip:PN_UE2b@home2.net>;index=1,  <sip:PN_UE2a@home2.net;target=PN_UE-2b@home2.-   net>;index=1.1Accept-Contact:*;g.3gpp.app_ref=“urn%3Aurn-xxx%3A3gpp- application.ims.iari.PNM-Controller” P-Asserted-Service:urn:urn-xxx:3gpp-service.ims.icsi.mmtel Allow: INVITE, ACK, CANCEL, BYE,PRACK, UPDATE, REFER, MESSAGE P-Called-Party-ID: <sip:PN_UE2a@home2.-net;target=PN_UE-2b@home2.net> Content-Type: application/sdpContent-length: (...) SDP NOT SHOWN

FLOW 12. 100 Trying

UE-2a responds to the INVITE#2 request with a 100 Trying provisionalresponse. An example of the resulting 100 Trying provisional responsemay be as follows:

12: SIP 100 Trying

SIP/2.0 100 Trying Via:SIP/2.0/UDPscscf2.home2.net;branch=z9hG4bwt871y12.1, SIP/2.0/UDPpnmas.home2.net;branch=v7hG4bwt171y12.1 From:<sip:pnmas.home1.net>;tag=r3rw33 To: <sip:PN_UE2a@home2.net> Cseq: 127INVITE Call-ID:131243vdse Content-Length: 0

FLOW 13. PNM Privacy Decision

Based upon the IARI value PNM Controller UE 102 invokes the PNMController application 406. The PN Controller application 406 providesthe originator's identity from the P-Asserted-Identity header, the PNMControllee UE 104 identity from the target URI-parameter in theRequest-URI, and the option for the user to:

1: forward the session to the PNM Controllee UE 104;

2: reject the session; and/or

3: accept the session.

In the example that follows, the user determines to forward the call (orsession) to the PNM Controllee UE 104.

FLOW 14. 302 Moved Temporarily

The PNM Controllee UE 104 sends a SIP 302 Moved Temporarily response topcscf2a.visited2.net. An example of the SIP 302 Moved Temporarilyresponse at this flow may be as follows:

14; SIP 302 Moved Temporarily

SIP/2.0 302 Moved Temporarily Via: SIP/2.0/UDPpcscf2.visited2.net;branch=z9hG4bK240f34.1, SIP/2.0/UDPscscf2.home2.net;branch=z9hG4bwt871y12.1, SIP/2.0/UDPpnmas.home2.net;branch=k9hG4bwt871y12.1 From:<sip:pnmas.home1.net>;tag=r3rw33 To: <sip:PN_UE2a@home2.net>;tag=wd689Cseq: 127 INVITE Call-ID:131243vdse History-Info:<sip:PN_UE2b@home2.net>;index=1,  <sip:PN_UE2a@home2.net;target=PN_UE-2b@home2.-   net>;index=1.1Contact: <sip:PN_UE2b@home2.net> Content-Length:0

As illustrated above, the SIP 302 Moved Temporarily response providesthe following information:

Contact: provides a URI that contains the address of the PNM ControlleeUE 104 (PN_UE-2b@home2.net).

History-info: contains the URIs from the History-Info header in theoriginal INVITE (PN_UE-2b@home2.net and PN_UE2a@home2.net;target=PN_UE-2b@home2.net). The PNM Controller may look to thecontents of the History-Info header and responsive to finding the targetparameter set to the URI of the Controllee, invoke the PNM Controllerfunction . . . .

15. 302 Moved Temporarily

The P-CSCF#2a forwards the 302 Moved Temporarily response to theS-CSCF#2. An example of the forwarded 302 Moved Temporarily response maybe as follows:

15: SIP 302 Moved Temporarily

SIP/2.0 200 OK Via: SIP/2.0/UDPscscf2.home2.net;branch=z9hG4bwt871y12.1, SIP/2.0/UDPpnmas.home2.net;branch=k9hG4bwt871y12.1 From:<sip:pnmas.home1.net>;tag=r3rw33 To: <sip:PN_UE2a@home2.net>;tag=wd689Cseq: 127 INVITE Call-ID:131243vdse History-Info:<sip:PN_UE2b@home2.net>;index=1,  <sip:PN_UE2a@home2.net;target=PN_UE-2b@home2.-   net>;index=1.1Contact: <sip:PN_UE2b@home2.net> Content-Length:0

FLOW 16. 302 Moved Temporarily

The S-CSCF#2 forwards the 200 OK to the PNM AS 106. An example of theforwarded 302 Moved Temporarily response at this flow may be as follows:

16: SIP 302 Moved Temporarily

SIP/2.0 200 OK Via: SIP/2.0/UDP pnmas.home2.net;branch=k9hG4bwt871y12.1From: <sip:pnmas.home1.net>;tag=r3rw33 To:<sip:PN_UE2a@home2.net>;tag=wd689 Cseq: 127 INVITE Call-ID:131243vdseHistory-Info: <sip:PN_UE2b@home2.net>;index=1, <sip:PN_UE2a@home2.net;target=PN_UE-2b@home2.net>;index=1.1 Contact:<sip:PN_UE2b@home2.net> Content-Length:0

FLOW 17. PNM Redirection Session Control

Upon receiving the 302 Moved Temporarily response from the PNMController UE 102, the PNM AS 106 determines that the session is to beredirected to the PNM Controllee UE 104.

FLOW 18. INVITE#3 (PNM AS to S-CSCF#2)

The PNM AS 106 forwards the originating INVITE message to the S-CSCF#2.An example of the INVITE message at this flow may be as follows:

18: SIP INVITE request (PNM AS to S-CSCF#2)

INVITE sip:PN_UE2b@home2.net Via:SIP/2.0/UDPpnmas.home2.net;branch=z9hG4bwt871y12.1 SIP/2.0/UDPscscf2.home2.net;branch=z9hG4bwt871y12.1, SIP/2.0/UDPicscf2.home2.net;branch=z9hG4bK871y12.1, SIP/2.0/UDPscscf1.home1.net;branch=z9hG4bK332b23.1, SIP/2.0/UDPpcscf1.visited1.net;branch=z9hG4bK240f34.1, SIP/2.0/UDP[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp;branch=z9hG4bKnashds7Max-Forwards: 63 Route: <sip:scscf2.home2.net;lr> Record-Route: <sip:scscf2.home1.net;lr>,<sip:scscf1.home1.net;lr>,<sip:pcscf1.visited.net;lr>P-Asserted-Identity: “John Doe” <sip:UE1@home1.net> Privacy: none From:<sip:UE1@home1.net>;tag=157893 To: <sip:UE2b@home2.net> Cseq: 127 INVITECall-ID:131243vdse Supported: precondition, 100rel, histinfo Contact:<sip:PN_UE2b@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765- 00a0c91e6bf6> History-Into: <sip:PN_UE2b@home2.net>;index=1,  <sip:PN_UE2a@home2.net;target=PN_UE-2b@home2.net>;index=1.1,  <sip:PN_UE2b@home2.net?Reason=SIP;cause=302>;index=1.2 Accept-Contact:*;g.3gpp.app_ref=“urn%3Aurn-xxx%3gpp-service.ims.icsi.mmtel”P-Asserted-Service: urn:urn-xxx:3gpp-service.ims.icsi.mmtel Allow:INVITE, ACK, CANCEL, BYE, PRACK, UPDATE, REFER, MESSAGE Content-Type:application/sdp Content-length: (...) SDP NOT SHOWN

As illustrated above, the INVITE message to the S-CSCF#2 provides thefollowing information:

Request-URI: contains the URI of the PNM Controller UE 102(PN_UE2a@home2.net) obtained from the Contact header in the (302 MovedTemporarily) response.

P-Asserted-Identity: contains the identity of the originator (“JohnDoe”<sip:UE1@home1.net>).

From: contains the SIP URI of the Originating UE (sip:UE1@home1.net).

To: contains the URI of the PNM Controller UE 102 (UE2a@home2.net).

Supported: contains the following option tags: precondition, 100rel,histinfo

Contact: contains the URI from the Contact header in the original INVITE(<sip:PN_UE2b@home1.net;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>).

History-info: contains the URIs from the History-info header in the 302Moved Temporarily response (PN_UE-2b@home2.net and PN_UE2a@home2.net;target=PN_UE-2b@home2.net) with the addition of the URI of the PNMControllee UE 104 (PN_UE-2b@home2.net) from the Contact header in the302 Moved Temporarily response along with the reason code “302”.

Accept-Contact: contains the contents of the Accept-Contact header inthe original INVITE (*;g.3gpp.app_ref=“urn %3Aurn-xxx%3gpp-service.ims.icsi.mmtel”).

Flows 19-34 follow the standard session establishment proceduresspecified in TS 24.229[10].

Alternatively, in order to enable the PNM Controller UE 102 to identifythe SIP INVITE request as a PNM Controller application 406 relatedrequest as opposed to an ordinary call or session or message andcall/message forwarding, the PNM AS 106 may add identifiers to the SIPINVITE or other SIP request. According to an embodiment of thedisclosure, the resulting SIP INVITE may be as follows:

SIP INVITE Request (PNM AS to S-CSCF#2)

INVITE sip:PN_UE2a@home1.net;3gpp-pnm-cntrlr Via: SIP/2.0/UDPpnmas.home1.net;branch=z9hG4bwt871y12.1 Max-Forwards: 70 Route:<sip:scscf1.home1.net;lr> P-Asserted-Identity: “John Doe”<sip:UE1@home1.net> Privacy: none From: <sip:pnmas.home1.net>;tag=r3rw33To: <sip:UE2a@home1.net;3gpp-pnm-cntrlr> Cseq: 127 INVITECall-ID:131243vdse Supported: precondition, 100rel, histinfoHistory-Info: <sip:PN_UE2b@home1.net>;index=1,  <sip:PN_UE2a@home1.net;3gpp-pnm-cntrlr?Reason=3GPP- PNM;cause=1>;index=1.1 Accept-Contact: *;g.3gpp.app_ref=“urn%3Aurn-xxx%3A3gpp- application.ims.iari.PNM-Controller” Contact:<sip:pnmas.home1.net;3gpp-pnm-cntrlr> Allow: INVITE, ACK, CANCEL, BYE,PRACK, UPDATE, REFER, MESSAGE Content-Type: application/sdpContent-length: (...) SDP NOT SHOWN

The identifiers in the above example maybe:

1: a PNM specific URI-parameter (3GPP-pnm-cntrlr) added to the URI ofthe PNM Controller UE 102 in the Request URI and/or a PNM specificURI-parameter (3GPP-pnm-cntrlr) added to the URI in the To header;

2: a Reason header in a History-Info header, the Reason headerindicating that this is a PNM Controller application 406 relatedforwarding (Reason=3GPP-PNM;cause=1, where 1 indicates PNM Controllerapplication 406 related forwarding). The PNM Controller UE 102 URI inthe History-Info header also may contain a PNM specific URI-parameter(3GPP-pnm-cntrlr); and

3: a media feature tag (g.3gpp.app_ref=″urn %3Aurn-xxx%3A3gpp-application.ims.iari.PNM-Controller) in the Accept-Contactheader, the media feature tag identifies the PNM Controller application406.

When the S-CSCF#2 receives the above SIP INVITE request, the S-CSCF#2will copy the Request-URI containing the URI of the PNM Controller UE102 into the P-Called-Party-ID header and rewrite the Request-URI to theregistered Contact address of the PNM Controller UE 102.

While P-Called-Party-ID header is one embodiment, the Request-URI maynot always be copied into the P-Called-Party-ID header. Proposals existto change this behavior and it is possible in the future that theRequest-URI may not be overwritten by the Contact (as proposed indraft-rosenberg-sip-ua-loose-route-01) or a new header other than theP-Called-Party-ID header may be used (e.g the target header proposed indraft-holmberg-sip-target-uri-delivery-00) to transport the originalRequest-URI. Alternatively, the target URI-parameter may be used totransport the original Request-URI. The PNM Controller would then obtainthe Request-URI contents using these means.

According to an embodiment of the disclosure, the resulting the SIPINVITE request may be as follows:

Alternative SIP INVITE Request (P-CSCF#2 to UE-2a)

INVITE sip:[5555::eee:fff:aaa:bbb]:8805;comp=sigcomp SIP/2.0 Via:SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bwt871y12.1 Via: SIP/2.0/UDPpnmas.home1.net;branch=k9hG4bwt871y12.1 Max-Forwards: 68 Record-Route:<sip:scscf1.home1.net;lr>,<sip:pcscf1.visited1.net;lr>P-Asserted-Identity: “John Doe” <sip:UE1@home1.net> Privacy: none From:<sip:pnmas.home1.net>; tag=r3rw33 To:<sip:UE2a@home1.net;3gpp-pnm-cntrlr> Cseq: 127 INVITE Call-ID:131243vdse Supported: precondition, 100rel, histinfo History-Info:<sip:PN_UE2b@home1.net>;index=1,  <sip:PN_UE2a@home1.net;3gpp-pnm-cntrlr?Reason=3GPP- PNM;cause=1>;index=1.1 Accept-Contact: *;g.3gpp.app_ref=“urn%3Aurn-xxx%3A3gpp- application.ims.iari.PNM-Controller” Contact:<sip:pnmas.home1.net;3gpp-pnm-cntrlr> Allow: INVITE, ACK, CANCEL, BYE,PRACK, UPDATE, REFER, MESSAGE P-Called-Party-ID:<sip:PN_UE2a@home1.net;3gpp-pnm-cntrlr> Content-Type: application/sdpContent-length: (...) SDP NOT SHOWN

When the PNM Controller UE 102 receives the above SIP INVITE request,the PNM Controller UE 102 can use the following aspects to determinethat this is a PNM Controller application 406 related request as opposedto an ordinary call or call forwarding:

1: the presence of a PNM specific URI-parameter (3GPP-pnm-cntrlr) in theP-Called-Party-ID header and/or the PNM specific URI-parameter(3GPP-pnm-cntrlr) added to the To header;

2: the presence of the Reason header indicating that this is a PNMController application 406 related forwarding (Reason=3GPP-PNM;cause=1,where 1 indicates the PNM Controller application 406 related forwarding)in the History-Info header;

3. the presence of the PNM specific URI-parameter (3GPP-pnm-cntrlr) inthe URI in the History-Info header; and/or

4: the presence of a media feature tag (or parameter value of the mediafeature tag g.3gpp.app_ref=″urn %3Aurn-xxx%3A3gpp-application.ims.iari.PNM-Controller) in the Accept-Contactheader that identifies the PNM Controller application 406.

5: The presence in the Contact header of a PNM specific URI-parameter(3GPP-pnm-cntrlr), which may be added by the PNM Application Server.

Alternatively, the target URI parameter mechanism maybe used. In thisembodiment, the PNM AS 106 adds a target URI parameter to the SIP INVITErequest. According to an embodiment of the disclosure, the resulting SIPINVITE may be as follows:

Alternative SIP INVITE Request (PNM AS to S-CSCF#2)

INVITE sip:PN_UE2a@home1.net;target=PN_UE-2b@home1.net Via: SIP/2.0/UDPpnmas.home1.net;branch=z9hG4bwt871y12.1 Max-Forwards: 70 Route:<sip:scscf1.home1.net;lr> P-Asserted-Identity: “John Doe”<sip:UE1@home1.net> Privacy: none From: <sip:pnmas.home1.net>;tag=r3rw33To: <sip:UE2a@home1.net;3gpp-pnm-cntrlr> Cseq: 127 INVITECall-ID:131243vdse Supported: precondition, 100rel, histinfoHistory-Info: <sip:PN_UE2b@home1.net>;index=1,  <sip:PN_UE2a@home1.net;3gpp-pnm-cntrlr?Reason=3GPP- PNM;cause=1>;index=1.1 Accept-Contact: *;g.3gpp.app_ref=“urn%3Aurn-xxx%3A3gpp- application.ims.iari.PNM-Controller Contact:<sip:pnmas.home1.net;3gpp-pnm-cntrlr> Allow: INVITE, ACK, CANCEL, BYE,PRACK, UPDATE, REFER, MESSAGE Content-Type: application/sdpContent-length: (...) SDP NOT SHOWN

When the S-CSCF#2 receives the above SIP INVITE request, the S-CSCF#2will copy the Request-URI containing the URI of the PNM Controller UE102 into the P-Called-Party-ID header and rewrite the Request-URI to theregistered Contact address of the PNM Controller UE 102, According to anembodiment of the disclosure, the resulting the SIP INVITE request maybe as follows:

Alternative SIP INVITE request (P-CSCF#2 to UE-2a)

INVITE sip:[5555::eee:fff:aaa:bbb]:8805;comp=sigcomp SIP/2.0 Via:SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bwt871y12.1 Via: SIP/2.0/UDPpnmas.home1.net;branch=k9hG4bwt871y12.1 Max-Forwards: 68 Record-Route:<sip:scscf1.home1.net;lr>,<sip:pcscf1.visited1.net;lr>P-Asserted-Identity: “John Doe” <sip:UE1@home1.net> Privacy: none From:<sip:pnmas.home1.net>; tag=r3rw33 To:<sip:UE2a@home1.net;3gpp-pnm-cntrlr> Cseq: 127 INVITE Call-ID:131243vdse Supported: precondition, 100rel, histinfo History-Info:<sip:PN_UE2b@home1.net>;index=1,  <sip:PN_UE2a@home1.net;3gpp-pnm-cntrlr?Reason=3GPP- PNM;cause=1>;index=1.1 Accept-Contact: *;g.3gpp.app_ref=“urn%3Aurn-xxx%3A3gpp- application.ims.iari.PNM-Controller Contact:<sip:pnmas.home1.net;3gpp-pnm-cntrlr > Allow: INVITE, ACK, CANCEL, BYE,PRACK, UPDATE, REFER, MESSAGE P-Called-Party-ID: <sip:PN_UE2a@home1.-net;target=PN_UE-2b@home1.net> Content-Type: application/sdpContent-length: (...) SDP NOT SHOWN

When the PNM Controller UE 102 receives the above SIP INVITE request,the PNM Controller UE 102 can use the following aspects to determinethat this is a PNM Controller application 406 related request as opposedto an ordinary call or call forwarding:

1: the presence of the target URI parameter in the P-Called-Party-IDheader containing either a URI that identifies the PNM Controllerapplication or the URI of the PNM Controllee UE 104. In this example,the target URI parameter contains the URI of the PNM Controllee UE 104(PN_UE-2b@home1.net); or

2: the presence of the media feature tag (or parameter value of themedia feature tag, e.g g.3gpp.app_ref=″urn %3Aurn-xxx%3A3gpp-application.ims.iari.PNM-Controller Contact:<sip:pnmas.home1.net>) in the Accept-Contact header that identifies thePNM Controller application 406.

An alternative to using a PNM specific URI-parameter to identify the PNMController application 406 is to use a PNM Controller specific URI. ThisURI can be either explicitly or implicitly registered by the PNMController UE 102. In this embodiment, the PNM Controller specific URI(e.g., PNM-Controller-UE2a@home1.net) can be used where the PNMController UE 102 URI (PN_UE-2a@home1.net) along with the PNM specificURI-parameter (3GPP-pnm-cntrlr) is used in the previous figures.

Another possibility is that a new SIP header could be used to convey andindication that this is a PNM Controller application 406 relatedrequest.

Once the PNM Controller UE 102 has received the SIP INVITE andidentified that the SIP INVITE is a PNM Controller application 406related request, the PNM Controller application 406 will alert the userand indicate to the user the identity of the caller (based on theP-Asserted-Identity header contents) and the identity of the PNMControllee UE 104 (from the History-info header). The user of the PNMController UE 102 can then decide to:

1: accept the call (or session or message) themselves (return a SIP 200OK response or a 2XX response);

2: redirect the call (or session or message) to the PNM Controllee UE104 (or return a SIP 302 or 3XX or 4XX response); or

3: reject the call (or session or message) (return a SIP 4xx Response).

If the user decides to redirect the call (or session or message) to thePNM Controllee UE 104, the PNM Controller UE 102 responds with a SIP 302Moved Temporarily response. In an embodiment of the disclosure, the SIP302 Moved Temporarily response may be as follows:

SIP 302 Moved Temporarily

SIP/2.0 302 Moved Temporarily Via:SIP/2.0/UDPscscf1.home1.net;branch=z9hG4bwt871y12.1 Via:SIP/2.0/UDPpnmas.home1.net;branch=v7hG4bwt171y12.1 From:<sip:pnmas.home1.net>;tag=r3rw33 To:<sip:UE2a@home1.net;3gpp-pnm-cntrlr>;tag=314159 Call-ID: 131243vdseCSeq: 127 INVITE History-Info: <sip:PN_UE2b@home1.net>;index=1,  <sip:PN_UE2a@home1.net;3gpp-pnm-cntrlr?Reason=3GPP- PNM;cause=1>;index=1.1 Contact: <sip:PN_UE2b@home1.net>Content-Length:0

The above SIP 302 Moved Temporarily response includes:

1: a Contact header containing the URI of the PNM Controllee UE 104; and

2: a History-Info header containing the Reason header indicating thatthis is a PNM Controller application 406 related forwarding and the PNMspecific URI-parameter (3GPP-pnm-cntrlr).

When the PNM AS 106 receives the above SIP 302 Moved Temporarilyresponse, the PNM AS 106 redirects the SIP INVITE request to the PNMControllee UE 104 based on the URI in the Contact header. According toan embodiment of the disclosure, the resulting the SIP INVITE requestmay be as follows:

SIP INVITE Request (PNM AS to S-CSCF#2)

INVITE sip:PN_UE2b@home1.net Via: SIP/2.0/UDPpnmas.home1.net;branch=z9hG4bwt871y12.1 Max-Forwards: 70 Route:<sip:scscf1.home1.net;lr> P-Asserted-Identity: “John Doe”<sip:UE1@home1.net> Privacy: none From: <sip:pnmas.home1.net>;tag=734756To: <sip:UE2b@home1.net> Cseq: 127 INVITE Call-ID:131243vdse Supported:precondition, 100rel, histinfo History-Info:<sip:PN_UE2b@home1.net>;index=1,  <sip:PN_UE2a@home1.net;3gpp-pnm-cntrlr?Reason=3GPP- PNM;cause=1>;index=1.1,   <sip:PN_UE2b@home1.-  net?Reason=SIP;cause=302;3gpp-pnm-cntrlr>;index=1.2 Contact:<sip:pnmas.home1.net> Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE,REFER, MESSAGE Content-Type: application/sdp Content-length: (...)

The History-Info header is included with the contents of theHistory-Info from the SIP 302 Moved Temporarily response with the URI ofthe PNM Controllee UE 104 added along with the reason code 1204 (Cause302).

According to an embodiment of the disclosure, when the S-CSCF receivesthe above SIP INVITE request, the S-CSCF will copy the Request-URIcontaining the URI of the PNM Controllee UE 104 into theP-Called-Party-ID header and rewrite the Request-URI to the registeredContact address of the PNM Controllee UE 104. In an embodiment of thedisclosure, the resulting request may be as follows:

SIP INVITE Request (P-CSCF#2 to UE-2a)

INVITE sip:[5555::eee:fff:aaa:bbb]:8805;comp=sigcomp SIP/2.0 Via:SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bwt871y12.1 Via: SIP/2.0/UDPpnmas.home1.net;branch=k9hG4bwt871y12.1 Max-Forwards: 68 Record-Route:<sip:scscf1.home1.net;lr>,<sip:pcscf1.visited1.net;lr>P-Asserted-Identity: “John Doe” <sip:UE1@home1.net> Privacy: none From:<sip:pnmas.home1.net>; tag=r3rw33 To: <sip:UE2b@home1.net> Cseq: 127INVITE Call-ID: 131243vdse Supported: precondition, 100rel, histinfoHistory-Info: <sip:PN_UE2b@home1.net>;index=1,  <sip:PN_UE2a@home1.net;3gpp-pnm-cntrlr?Reason=3GPP- PNM;cause=1>;index=1.1,   <sip:PN_UE2a@home1.-  net?Reason=SIP;cause=302;3gpp-pnm-cntrlr>;index=1.2 Contact:<sip:pnmas.home1.net> Allow: INVITE, ACK, CANCEL, BYE, PRACK, UPDATE,REFER, MESSAGE P-Called-Party-ID: <sip:PN_UE1b@home1.net> Content-Type:application/sdp Content-length: (...)

The PNM Controllee UE 104 is then able to accept the call (or session ormessage) with a SIP 200 OK response.

In the case that the PNM Controller application 406 accepts the call (orsession or message) and then decides to transfer the call (or session)to the PNM Controllee UE 104, the PNM Controller application 406 can usethe Explicit Call Transfer mechanism defined in 3GPP TS 24.173 totransfer the call (or session) to the PNM Controllee UE 104.

Alternatively, if PNM Controller UE 102 has a list for all thecontrollee UEs in its PNM, then the presence of the URI of the PNMControllee UE 104 in the History-Info header can be used to determinethat this is a PNM Controller application 406 related request as opposedto an ordinary call or call forwarding.

However, this has the disadvantage that it may not be possible for thePNM Controllee UE 104 to redirect or otherwise forward requests as theserequests will also be treated as PNM Controller application 406requests.

Furthermore, within the device there could be provisioned one or morePNM URIs lists. Within each list may be any number of URIs which arevalid controllee URIs for that controller group. These lists could beprovisioned via OMA DM, MBMS, cell broadcast SMS, USSD OTA, or via inputmechanism on the device. The list of valid URIs could be stored onmemory inside the device or external memory (U)SIM, Compact flash,MicroSD, memory stick, etc.

When a SIP INVITE is received with a TARGET SIP URI in the P-CALLEDHEADER or Request URI (R-URI), the device will check the URI associatedwith the TARGET against the URIs provisioned in the PNM URI lists. Ifthe URI appears in a URI list, the device will know which group thisdevice should act as a PNM Controller UE. If the URI does not exist thedevice could:

1: reject the invite;

2: process the invite per a default PNM group; and/or

3: process the invite after subsequent input received via an inputmechanism on the device.

In an embodiment of the disclosure, the format of the stored URI may beas follows:

SIP URI (U)SIM format Identifier: ‘xxx’ Structure: linear fixedMandatory SFI: ‘04’ Record length: X bytes Update activity: low AccessConditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM BytesDescription M/O Length 1 to X URI TLV data object M X bytes

URI

-   -   Contents:        -   SIP URI by which other parties know the subscriber.    -   Coding:        -   For contents and coding of URI TLV data object values see            IETF RFC 3261[16]. The tag value of the URI TLV data object            shall be ‘80’.

OMA DM type

/<X>/PNM URI/

-   -   Occurrence: One    -   Format: chr    -   Access Types: Get, Replace    -   Values: <A PNM URI>

The format of the PNM URI is defined by 3GPP TS 23.003[2].

For example, the format of the PNM URI, sip:domain.xfer@dtf1.home1.net,is as follows:

<Node>  <NodeName> PNM URI </NodeName>  <!-- The PNM URI node startshere. -->  <DFProperties>   <AccessType>     <Get/>     <Replace/>  </AccessType>   <DFFormat>     <chr/>   </DFFormat>   <Occurrence>    <One/>    </Occurrence>   <DFTitle>The PNM URI .</DFTitle>  <DFType>     <DDFName>   </DFType>  </DFProperties> </Node>

The calls or sessions established or messages received using thesemechanisms can be a voice call, a multimedia session, a messagingsession, or any other media that can be established using SIP INVITE orother SIP Request. As well as SIP INVITE, the mechanisms defined herecan also be used with SIP MESSAGE method.

The privacy service authorizes the call where the authorization is apartfrom normal authorization procedures involved in the network andrequires real time consent from the user. All other supplementaryfeatures or other services may follow once this authorization isreceived.

While only one Controller UE and one controllee UE are depicted for easeof discussion, persons of ordinary skill in the art will recognize thatany number of controller and controllee UEs may be present.

FIG. 6 illustrates a wireless communications system including anembodiment of the UE 102. The UE 102 is operable for implementingaspects of the disclosure, but the disclosure should not be limited tothese implementations. Though illustrated as a mobile phone, the UE 102may take various forms including a wireless handset, a pager, a personaldigital assistant (PDA), a portable computer, a tablet computer, or alaptop computer, wireless or wired or fixed devices including standardwired telephone handset, set-top boxes, and the like. Many suitabledevices combine some or all of these functions. In some embodiments ofthe disclosure, the UE 102 is not a general purpose computing devicelike a portable, laptop or tablet computer, but rather is aspecial-purpose communications device such as a mobile phone, wirelesshandset, pager, or PDA. In another embodiment, the UE 102 may be aportable, laptop or other computing device. The UE 102 may supportspecialized activities such as gaming, inventory control, job control,and/or task management functions, and so on.

The UE 102 includes a display 602. The UE 102 also includes atouch-sensitive surface, a keyboard or other input keys generallyreferred as 604 for input by a user. The keyboard may be a full orreduced alphanumeric keyboard such as QWERTY, Dvorak, AZERTY, andsequential types, or a traditional numeric keypad with alphabet lettersassociated with a telephone keypad. The input keys may include atrackwheel, an exit or escape key, a trackball, and other navigationalor functional keys, which may be inwardly depressed to provide furtherinput function. The UE 102 may present options for the user to select,controls for the user to actuate, and/or cursors or other indicators forthe user to direct. The UE 102 may further accept data entry from theuser, including numbers to dial or various parameter values forconfiguring the operation of the UE 102. The UE 102 may further executeone or more software or firmware applications in response to usercommands. These applications may configure the UE 102 to perform variouscustomized functions in response to user interaction. Additionally, theUE 102 may be programmed and/or configured over-the-air, for examplefrom a wireless base station, a wireless access point, or a peer UE 102.

Among the various applications executable by the UE 102 are a webbrowser, which enables the display 602 to show a web page. The web pagemay be obtained via wireless communications with a wireless networkaccess node, a cell tower, a peer UE 102, or any other wirelesscommunication network or system. The network is coupled to a wirednetwork 608, such as the Internet. Via the wireless link and the wirednetwork, the UE 102 has access to information on various servers, suchas a server 610. The server 610 may provide content that may be shown onthe display 602. Alternately, the UE 102 may access the network througha peer UE 102 acting as an intermediary, in a relay type or hop type ofconnection.

FIG. 7 shows a block diagram of the UE 102. While a variety of knowncomponents of the UE 102 is depicted, in an embodiment a subset of thelisted components and/or additional components not listed may beincluded in the UE 102. The UE 102 includes a central processing unit(CPU) 702 and a memory 704. As shown, the UE 102 may further include anantenna and front end unit 706, a radio frequency (RF) transceiver 708,an analog baseband processing unit 710, a microphone 712, an earpiecespeaker 714, a headset port 716, an input/output interface 718, aremovable memory card 720, a universal serial bus (USB) port 722, ashort range wireless communication sub-system 724, an alert 726, akeypad 728, a liquid crystal display (LCD), which may include a touchsensitive surface 730, an LCD Controller 732, a charge-coupled device(CCD) camera 734, a Camera Controller 736, and a global positioningsystem (GPS) sensor 738. In an embodiment, the UE 102 may includeanother kind of display that does not provide a touch sensitive screen.In an embodiment, the CPU 702 may communicate directly with the memory704 without passing through the input/output interface 718.

The CPU 702 or some other form of Controller or central processing unitoperates to control the various components of the UE 102 in accordancewith embedded software or firmware stored in memory 704 or stored inmemory contained within the CPU 702 itself. In addition to the embeddedsoftware or firmware, the CPU 702 may execute other applications storedin the memory 704 or made available via information carrier media suchas portable data storage media like the removable memory card 720 or viawired or wireless network communications. The application software maycomprise a compiled set of machine-readable instructions that configurethe CPU 702 to provide the desired functionality, or the applicationsoftware may be high-level software instructions to be processed by aninterpreter or compiler to indirectly configure the CPU 702.

The antenna and front end unit 706 may be provided to convert betweenwireless signals and electrical signals, enabling the UE 102 to send andreceive information from a cellular network or some other availablewireless communications network or from a peer UE 102. In an embodiment,the antenna and front end unit 706 may include multiple antennas tosupport beam forming and/or multiple input multiple output (MIMO)operations. As is known to those skilled in the art, MIMO operations mayprovide spatial diversity which can be used to overcome difficultchannel conditions and/or increase channel throughput. The antenna andfront end unit 706 may include antenna tuning and/or impedance matchingcomponents, RF power amplifiers, and/or low noise amplifiers.

The RF transceiver 708 provides frequency shifting, converting receivedRF signals to baseband and converting baseband transmit signals to RF.In some descriptions a radio transceiver or RF transceiver may beunderstood to include other signal processing functionality such asmodulation/demodulation, coding/decoding, interleaving/deinterleaving,spreading/despreading, inverse fast Fourier transforming (IFFT)/fastFourier transforming (FFT), cyclic prefix appending/removal, and othersignal processing functions. For the purposes of clarity, thedescription here separates the description of this signal processingfrom the RF and/or radio stage and conceptually allocates that signalprocessing to the analog baseband processing unit 710 and/or the CPU 702or other central processing unit. In some embodiments, the RFTransceiver 708, portions of the Antenna and Front End 706, and theanalog baseband processing unit 710 may be combined in one or moreprocessing units and/or application specific integrated circuits(ASICs).

The analog baseband processing unit 710 may provide various analogprocessing of inputs and outputs, for example analog processing ofinputs from the microphone 712 and the headset 716 and outputs to theearpiece 714 and the headset 716. To that end, the analog basebandprocessing unit 710 may have ports for connecting to the built-inmicrophone 712 and the earpiece speaker 714 that enable the UE 102 to beused as a cell phone. The analog baseband processing unit 710 mayfurther include a port for connecting to a headset or other hands-freemicrophone and speaker configuration. The analog baseband processingunit 710 may provide digital-to-analog conversion in one signaldirection and analog-to-digital conversion in the opposing signaldirection. In some embodiments, at least some of the functionality ofthe analog baseband processing unit 710 may be provided by digitalprocessing components, for example by the CPU 702 or by other centralprocessing units.

The CPU 702 may perform modulation/demodulation, coding/decoding,interleaving/deinterleaving, spreading/despreading, inverse fast Fouriertransforming (IFFT)/fast Fourier transforming (FFT), cyclic prefixappending/removal, and other signal processing functions associated withwireless communications. In an embodiment, for example in a codedivision multiple access (CDMA) technology application, for atransmitter function the CPU 702 may perform modulation, coding,interleaving, and spreading, and for a receiver function the CPU 702 mayperform despreading, deinterleaving, decoding, and demodulation. Inanother embodiment, for example in an orthogonal frequency divisionmultiplex access (OFDMA) technology application, for the transmitterfunction the CPU 702 may perform modulation, coding, interleaving,inverse fast Fourier transforming, and cyclic prefix appending, and fora receiver function the CPU 702 may perform cyclic prefix removal, fastFourier transforming, deinterleaving, decoding, and demodulation. Inother wireless technology applications, yet other signal processingfunctions and combinations of signal processing functions may beperformed by the CPU 702.

The CPU 702 may communicate with a wireless network via the analogbaseband processing unit 710. In some embodiments, the communication mayprovide Internet connectivity, enabling a user to gain access to contenton the Internet and to send and receive e-mail or text messages. Theinput/output interface 718 interconnects the CPU 702 and variousmemories and interfaces. The memory 704 and the removable memory card720 may provide software and data to configure the operation of the CPU702. Among the interfaces may be the USB interface 722 and the shortrange wireless communication sub-system 724. The USB interface 722 maybe used to charge the UE 102 and may also enable the UE 102 to functionas a peripheral device to exchange information with a personal computeror other computer system. The short range wireless communicationsub-system 724 may include an infrared port, a Bluetooth interface, anIEEE 802.11 compliant wireless interface, or any other short rangewireless communication sub-system, which may enable the UE 102 tocommunicate wirelessly with other nearby mobile devices and/or wirelessbase stations.

The input/output interface 718 may further connect the CPU 702 to thealert 726 that, when triggered, causes the UE 102 to provide a notice tothe user, for example, by ringing, playing a melody, or vibrating. Thealert 726 may serve as a mechanism for alerting the user to any ofvarious events such as an incoming call, a new text message, and anappointment reminder by silently vibrating, or by playing a specificpre-assigned melody for a particular caller.

The keypad 728 couples to the CPU 702 via the interface 718 to provideone mechanism for the user to make selections, enter information, andotherwise provide input to the UE 102. The keyboard 728 may be a full orreduced alphanumeric keyboard such as QWERTY, Dvorak, AZERTY andsequential types, or a traditional numeric keypad with alphabet lettersassociated with a telephone keypad. The input keys may include atrackwheel, an exit or escape key, a trackball, and other navigationalor functional keys, which may be inwardly depressed to provide furtherinput function. Another input mechanism may be the LCD 730, which mayinclude touch screen capability and also display text and/or graphics tothe user. The LCD Controller 732 couples the CPU 702 to the LCD 730.

The CCD camera 734, if equipped, enables the UE 102 to take digitalpictures. The CPU 702 communicates with the CCD camera 734 via thecamera Controller 736. In another embodiment, a camera operatingaccording to a technology other than Charge Coupled Device cameras maybe employed. The GPS sensor 738 is coupled to the CPU 702 to decodeglobal positioning system signals, thereby enabling the UE 102 todetermine its position. Various other peripherals may also be includedto provide additional functions, e.g., radio and television reception.

FIG. 8 illustrates a software environment 802 that may be implemented bythe CPU 702. The CPU 702 executes operating system drivers 804 thatprovide a platform from which the rest of the software operates. Theoperating system drivers 804 provide drivers for the UE hardware withstandardized interfaces that are accessible to application software. Theoperating system drivers 804 include application management services(“AMS”) 806 that transfer control between applications running on the UE102. Also shown in FIG. 8 are a web browser application 808, a mediaplayer application 810, and Java applets 812. The web browserapplication 808 configures the UE 102 to operate as a web browser,allowing a user to enter information into forms and select links toretrieve and view web pages. The media player application 810 configuresthe UE 102 to retrieve and play audio or audiovisual media. The Javaapplets 812 configure the UE 102 to provide games, utilities, and otherfunctionality.

FIG. 9 illustrates a typical, general-purpose computer system 900 thatmay be suitable for implementing one or more embodiments disclosedherein. The computer system 900 includes a processor 920 (which may bereferred to as a central processor unit or CPU) that is in communicationwith memory devices including secondary storage 950, read only memory(ROM) 940, random access memory (RAM) 930, input/output (I/O) devices910, and network connectivity devices 960. The processor may beimplemented as one or more CPU chips.

The secondary storage 950 is typically comprised of one or more diskdrives or tape drives and is used for non-volatile storage of data andas an over-flow data storage device if RAM 930 is not large enough tohold all working data. Secondary storage 950 may be used to storeprograms which are loaded into RAM 930 when such programs are selectedfor execution. The ROM 940 is used to store instructions and perhapsdata which are read during program execution. ROM 940 is a non-volatilememory device which typically has a small memory capacity relative tothe larger memory capacity of secondary storage. The RAM 930 is used tostore volatile data and perhaps to store instructions. Access to bothROM 940 and RAM 930 is typically faster than to secondary storage 950.

I/O devices 910 may include printers, video monitors, liquid crystaldisplays (LCDs), touch screen displays, keyboards, keypads, switches,dials, mice, track balls, voice recognizers, card readers, paper tapereaders, or other well-known input devices.

The network connectivity devices 960 may take the form of modems, modembanks, ethernet cards, universal serial bus (USB) interface cards,serial interfaces, token ring cards, fiber distributed data interface(FDDI) cards, wireless local area network (WLAN) cards, radiotransceiver cards such as code division multiple access (CDMA) and/orglobal system for mobile communications (GSM) radio transceiver cards,and other well-known network devices. These network connectivity 960devices may enable the processor 920 to communicate with an Internet orone or more intranets. With such a network connection, it iscontemplated that the processor 920 might receive information from thenetwork, or might output information to the network in the course ofperforming the above-described method steps. Such information, which isoften represented as a sequence of instructions to be executed usingprocessor 920, may be received from and outputted to the network, forexample, in the form of a computer data signal embodied in a carrierwave.

Such information, which may include data or instructions to be executedusing processor 920 for example, may be received from and outputted tothe network, for example, in the form of a computer data baseband signalor signal embodied in a carrier wave. The baseband signal or signalembodied in the carrier wave generated by the network connectivity 960devices may propagate in or on the surface of electrical conductors, incoaxial cables, in waveguides, in optical media, for example opticalfiber, or in the air or free space. The information contained in thebaseband signal or signal embedded in the carrier wave may be orderedaccording to different sequences, as may be desirable for eitherprocessing or generating the information or transmitting or receivingthe information. The baseband signal or signal embedded in the carrierwave, or other types of signals currently used or hereafter developed,referred to herein as the transmission medium, may be generatedaccording to several methods well known to one skilled in the art.

The processor 920 executes instructions, codes, computer programs,scripts which it accesses from hard disk, floppy disk, optical disk(these various disk based systems may all be considered secondarystorage 950), ROM 940, RAM 930, or the network connectivity devices 960.

In traditional wireless telecommunications systems, transmissionequipment in a base station transmits signals throughout a geographicalregion known as a cell. As technology has evolved, more advanced networkaccess equipment has been introduced that can provide services that werenot possible previously. This advanced network access equipment mightinclude, for example, an enhanced node B (ENB) rather than a basestation or other systems and devices that are more highly evolved thanthe equivalent equipment in a traditional wireless telecommunicationssystem. Such advanced or next generation equipment may be referred toherein as long-term evolution (LTE) equipment. For LTE equipment, theregion in which a wireless device can gain access to atelecommunications network might be referred to by a name other than“cell”, such as “hot spot”. As used herein, the term “cell” will be usedto refer to any region in which a wireless device can gain access to atelecommunications network, regardless of whether the wireless device isa traditional cellular device, an LTE device, or some other device.

Devices that might be used by users in a telecommunications network caninclude both mobile terminals, such as mobile telephones, personaldigital assistants, handheld computers, portable computers, laptopcomputers, tablet computers and similar devices, and fixed terminalssuch as residential gateways, televisions, set-top boxes and the like.Such devices will be referred to herein as user equipment or UE.

A group of LTE-based cells might be under the control of a single entityknown as a central control. The central control typically manages andcoordinates certain activities with a group of cells such as thescheduling of transmissions and the control of a modulation and codingscheme for the cells. The modulation and coding schemes might includebinary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK),quadrature amplitude modulation (QAM), or other schemes that will befamiliar to one of skill in the art.

Services that might be provided by LTE-based equipment can includebroadcasts or multicasts of television programs, streaming video,streaming audio, and other multimedia content. Such services arecommonly referred to as multimedia broadcast multicast services (MBMS).An MBMS might be transmitted throughout a single cell or throughoutseveral contiguous or overlapping cells. A set of cells receiving anMBMS can be referred to as a service area. A service area and a regionunder the control of a central control do not necessarily coincide. Forexample, a central control might specify that a first subset of cellsunder its control will deliver a first MBMS and that a second subset ofcells under its control will deliver a second MBMS.

When multiple cells overlap, a UE within the overlapped region canreceive transmissions from multiple ENBs. It is well known in the artthat when a UE receives substantially identical data from a plurality ofENBs, the transmissions from the ENBs can augment one another to providea signal of significantly higher quality than would be the case if onlyone ENB were transmitting the signal. That is, a higher signal-to-noiseratio can be achieved when substantially the same data is transmitted atsubstantially the same time on substantially the same resource withsubstantially the same modulation and coding. A region in which aplurality of substantially identical signals are present is known as asingle frequency network, or SFN. In the case where all of the ENBs in aservice area are transmitting an MBMS with substantially identicalsignals, the service area can be referred to a multicast/broadcast SFN(MBSFN).

FIG. 10 illustrates an exemplary cellular network 1000 according to anembodiment of the disclosure. The cellular network 1000 may include aplurality of cells 1002 ₁, 1002 ₂, 1002 ₃, 1002 ₄, 1002 ₅, 1002 ₆, 1002₇, 1002 ₈, 1002 ₉, 1002 ₁₀, 1002 ₁₁, 1002 ₁₂, 1002 ₁₃, and 1002 ₁₄(collectively referred to as cells 1002). As is apparent to persons ofordinary skill in the art, each of the cells 1002 represents a coveragearea for providing cellular services of the cellular network 1000. Whilethe cells 1002 are depicted as having non-overlapping coverage areas,persons of ordinary skill in the art will recognize that one or more ofthe cells 1002 may have partially overlapping coverage with adjacentcells. Further, while a particular number of the cells 1002 aredepicted, persons of ordinary skill in the art will recognize that alarger or smaller number of the cells 1002 may be included in thecellular network 1000.

One or more UEs 10 may be present in each of the cells 1002. Althoughonly one UE 10 is depicted and is shown in only one cell 1002 ₁₂, itwill be apparent to one of skill in the art that a plurality of UEs 10might be present in each of the cells 1002. An ENB 20 in each of thecells 1002 performs functions similar to those of a traditional basestation. That is, the ENBs 20 provide a radio link between the UEs 10and other components in a telecommunications network. While the ENB 20is shown only in cell 1002 ₁₂, it should be understood that an ENB wouldbe present in each of the cells 1002. Also, radio links other than theENBs 20 could be used. A central control 1010 oversees the wireless datatransmissions within the cells 1002 by providing centralized managementand coordination for the cells 1002 and their corresponding ENBs 20.

In the present disclosure, the cellular systems or cells 1002 aredescribed as engaged in certain activities, such as transmittingsignals; however, as will be readily apparent to one skilled in the art,these activities would in fact be conducted by components comprising thecells. As an example, FIG. 11 depicts a more detailed view of the cell1002 ₁₂. The ENB 20 in cell 1002 ₁₂ can promote communication via atransmitter 27, a receiver 29, and/or other well known equipment.Similar equipment might be present in the other cells 1002. A pluralityof UEs 10 are present in the cell 1002 ₁₂, as might be the case in theother cells 1002.

The following references are hereby incorporated by reference for allpurposes:

[RFC 3261] SIP: Session Initiation Protocol, [RFC 4244] An Extension tothe Session Initiation Protocol (SIP) for Request History Information,[RFC 3326] The Reason Header Field for the Session Initiation Protocol(SIP), [RFC 4458] Session Initiation Protocol (SIP) URIs forApplications such as Voicemail and Interactive Voice Response (IVR),[RFC 3840] Indicating User Agent Capabilities in the Session InitiationProtocol (SIP), [RFC 3841] Caller Preferences for the Session InitiationProtocol (SIP), [3GPP TS 22.259], [3GPP TS 23.259], [3GPP TS 24.259],[3GPP TS 24.173], and Applying Loose Routing to Session InitiationProtocol (SIP) User Agents (UA) draft-rosenberg-sip-ua-loose-route-01,Target URI delivery in the Session Initiation Protocol (SIP)draft-holmberg-sip-target-uri-delivery-00.txt.

While several embodiments have been provided in the present disclosure,it should be understood that the disclosed systems and methods may beembodied in many other specific forms without departing from the spiritor scope of the present disclosure. The present examples are to beconsidered as illustrative and not restrictive, and the intention is notto be limited to the details given herein. For example, the variouselements or components may be combined or integrated in another systemor certain features may be omitted, or not implemented.

Also, techniques, systems, subsystems and methods described andillustrated in the various embodiments as discrete or separate may becombined or integrated with other systems, modules, techniques, ormethods without departing from the scope of the present disclosure.Other items shown or discussed as coupled or directly coupled orcommunicating with each other may be indirectly coupled or communicatingthrough some interface, device, or intermediate component, whetherelectrically, mechanically, or otherwise. Other examples of changes,substitutions, and alterations are ascertainable by one skilled in theart and could be made without departing from the spirit and scopedisclosed herein.

1. A server, comprising: a processor such that for a Session InitiationProtocol (SIP) request containing a Uniform Resource Identifier (URI)identifying the first device, the processor is programmed to promoteadding a URI and redirecting the SIP request to a second device, theadded URI used by the second device to invoke a Personal NetworkManagement (PNM) Controller function.
 2. The server of claim 1, whereinthe added URI is included in the Request-URI that identifiers the PNMController function.
 3. The server of claim 1, wherein the added URI isincluded in the To Header that identifies the PNM Controller function.4. The server of claim 1, wherein the added URI contains a URI-parameterthat identifies the PNM Controller function.
 5. The server of claim 1,wherein added URI with the URI-parameter is included in the History-Infoheader to identify the PNM Controller function.
 6. The server of claim4, wherein the URI-parameter is a target URI-parameter.
 7. The server ofclaim 6, wherein the target URI-parameter contains the URI of the PNMControllee User Equipment (UE).
 8. The server of claim 6, wherein thetarget URI-parameter contains a URI the identifies the PNM ControllerApplication.
 9. The server of claim 2, wherein the added URI contains aURI-parameter that identifies the PNM Controller function.
 10. Theserver of claim 3, wherein the added URI contains a URI-parameter thatidentifies the PNM Controller function.
 11. A method of redirecting aSession Initiation Protocol (SIP) request, comprising: receiving a SIPrequest addressed to a first device, the SIP request containing aUniform Resource Identifier (URI) identifying the first device; adding aURI to the SIP request; and redirecting the SIP request to a seconddevice; wherein the presence of the added URI invokes a controllerfunction that allows the second device to identify the SIP request as aredirected SIP request for the first device.
 12. The method of claim 11,wherein the added URI is included in the Request-URI that identifiersthe PNM Controller function.
 13. The method of claim 11, wherein theadded URI is included in the To Header that identifies the PNMController function.
 14. The method of claim 11, wherein the added URIcontains a URI-parameter that identifies the PNM Controller function.15. A server, comprising: a processor programmed to promote including ina request an identifier identifying a Personal Network Management (PNM)Controller function.
 16. The server of claim 15, wherein the identifieris defined as a Uniform Resource Identifier (URI) with a Reason includedin a History-Info header identifying the PNM Controller function. 17.The server of claim 15, wherein the identifier is defined as a SessionInitiated Protocol (SIP) header identifying the PNM Controller function.18. The server of claim 15, wherein the identifier is defined as anAccept-Contact header containing a media feature tag identifying the PNMController function.
 19. The server of claim 15, wherein the identifieris defined as a Contact header including a URI-parameter that identifiesthe PNM Controller function.
 20. A user equipment (UE), comprising: aprocessor such that responsive to receiving a Session InitiationProtocol (SIP) request including a Uniform Resource Identifier (URI)identifying a Personal Network Management (PNM) Controller function theprocessor is programmed to promote performing the PNM Controllerfunction.
 21. The UE of claim 20, wherein the URI identifying the PNMController function contains a URI-parameter that identifies the PNMController function.
 22. The UE of claim 21, wherein the URI-parameteris a target URI-parameter.
 23. The UE of claim 22, wherein the targetURI-parameter contains a URI of the PNM Controllee UE.
 24. The UE ofclaim 22, wherein the target URI-parameter contains a URI of the PNMController Application.
 25. The UE of claim 20, wherein the URI isobtained from at least one of a Request-URI, a P-Called Party-ID header,and a To header.
 26. The UE of claim 21, wherein the URI is obtainedfrom at least one of a Request-URI, a P-Called Party-ID header, and a Toheader.
 27. A user equipment (UE), comprising: a processor such thatresponsive to receiving a Session Initiation Protocol (SIP) requestincluding an identifier identifying a Personal Network Management (PNM)Controller function, the processor programmed to promote providing PNMController function.
 28. The UE of claim 27, wherein the identifier is amedia feature tag in the Accept-Contact header of the SIP request thatidentifies the PNM Controller function.
 29. The UE of claim 27, whereinthe identifier is a Uniform Resource Identifier (URI) with a Reasonheader in a History-info header of the SIP request that identifies thePNM Controller function.
 30. The UE of claim 27, wherein the identifieris defined as a Contact header including a URI-parameter that identifiesthe PNM Controller function.
 31. A user equipment (UE), comprising: aprocessor programmed to promote registration related to a PersonalNetwork Management (PNM) Controller function.
 32. The UE of claim 31,wherein the UE registers that the UE supports PNM Controller function byone of a feature tag and a parameter in a feature tag.
 33. The UE ofclaim 31, wherein the UE registers a Uniform Resource Identifier (URI)that identifies the PNM Controller function.